 $ type SYS$HELP:CDD032.RELEASE_NOTES












               VAX Common Data Dictionary Release Notes


                        Order No. AA-GK49A-TE



                           December 1985




          This manual contains the release notes for VAX Common Data
          Dictionary.






          Operating System:  VMS
                             MicroVMS

          Software Version:  VAX CDD V3.2






        digital equipment corporation, maynard, massachusetts

























The information in this document is subject to change
without notice and should not be construed as a
commitment by Digital Equipment Corporation.  Digital
Equipment Corporation assumes no responsibility for
any errors that may appear in this document.

The software described in this document is furnished
under a license and may be used or copied only in
accordance with the terms of such license.

No responsibility is assumed for the use or
reliability of software on equipment that is not
supplied by DIGITAL or its affiliated companies.


Copyright (c) 1981, 1982, 1983, 1984, 1985 by Digital
Equipment Corporation.  All rights reserved.


The postage paid READER'S COMMENTS form on the last
page of this document requests your critical
evaluation to assist us in preparing future
documentation.

The following are trademarks of Digital Equipment
Corporation:


ACMS           DECUS          UNIBUS
CDD            MicroVAX       VAX
DATATRIEVE     MicroVMS       VAXcluster
DEC            PDP            VAX Information
Architecture
DECgraph       Rdb/ELN        VMS
DECnet         Rdb/VMS        VT
DECslide       TDMS















                                   CONTENTS



CHAPTER 1       Release Notes

        1.1     New Features of CDD Version 3.2  . . . . . . . . . 1-1
        1.1.1     New Feature of DMU . . . . . . . . . . . . . . . 1-1
        1.1.2     New Features of CDDL . . . . . . . . . . . . . . 1-2
        1.2     CDD Version 3.2 and VAX/VMS Version 4.0  . . . . . 1-3
        1.3     Installing CDD on a Cluster  . . . . . . . . . . . 1-3
        1.4     Underscore Preceding CDD_$TOP  . . . . . . . . . . 1-4
        1.5     Using Multiple Versions of CDD Objects with VAX 
                DATATRIEVE . . . . . . . . . . . . . . . . . . . . 1-4
        1.6     The VAX Data Base Management System and CDDEXC.EXE 1-4
        1.7     Installing CDD with SYSPRV . . . . . . . . . . . . 1-5
        1.8     Path Names Pointing to Subdictionary Files . . . . 1-5
        1.9     The CDDL ALIGNED Clause  . . . . . . . . . . . . . 1-6
        1.10    Copying and Renaming a Dictionary Object Protected 
                by a Password  . . . . . . . . . . . . . . . . . . 1-6






















                        iii














                     Chapter 1

                   Release Notes

                   Release Notes



This document contains release information about the
VAX Common Data Dictionary, also referred to as the
CDD.



1.1  New Features of CDD Version 3.2

1.1  New Features of CDD Version 3.2

The following sections describe the new features of
the Dictionary Management Utility (DMU), the
Verify/Fix Utility (CDDV), and the CDD Data
Definition Language Utility (CDDL).



1.1.1  New Feature of DMU

1.1.1  New Feature of DMU

With Version 3.2 of the VAX Common Data Dictionary
(CDD) you can use 8-bit characters in field names
and path names, if you are using a terminal of the
VT200 family.  For more information about field
                                               ___

names, see Sections 2.6, 2.12, and 2.22 of the VAX
______ ____ __________ ____ __________ ________

Common Data Dictionary Data Definition Language
_________ ______

Reference Manual.  For more information about path
                              ___ ______ ____

names, see Section 2.3 in the VAX Common Data


                        1-1



Release Notes

Release Notes


__________ ______ _____

Dictionary User's Guide.  For information about file
specifications, see the VAX/VMS documentation set.



1.1.2  New Features of CDDL

1.1.2  New Features of CDDL

New features of the CDD Data Definition Language
Utility (CDDL) include:

o  Further support of the 8-bit character set.  If
   you are using a terminal of the VT200 family, you
   can now use 8-bit alphabetic characters in field
   names and path names.  Remember that other
   terminals cannot reproduce 8-bit characters.  For
   more information about field names, see Sections
                              ___ ______ ____

   2.6, 2.12, and 2.22 of the VAX Common Data
   __________ ____ __________ _________ _______

   Dictionary Data Definition Reference Manual.  For
   more information about path names, see Section
              ___ ______ ____ __________ ______

   2.3 of the VAX Common Data Dictionary User's
   ______

   Guide.

o  Support for VAX RPG II.  You can use three CDDL
   field attribute clauses for VAX RPG II:
   EDIT__CODE FOR RPG, EDIT__WORD FOR RPG, and NAME
   FOR RPG.

                         NOTE


       Although the CDD now supports VAX RPG II,
       VAX RPG II will not provide matching
       support until a future release.


o  Support for the COBOL VALUE IS EXTERNAL clause.
   You can use VALUE IS EXTERNAL with two field
   attribute clauses, CONDITION NAME and
   INITIAL__VALUE.  EXTERNAL allows you to specify a
   quoted string.  For more information about this


                        1-2



                                       Release Notes

                                       Release Notes


   clause, see Sections 2.5 and Section 2.13 of the
   ___ ______ ____ __________ ____ __________

   VAX Common Data Dictionary Data Definition
   ________ _________ ______

   Language Reference Manual.

                         NOTE


       Although the CDD now supports this
       clause, VAX COBOL will not provide
       matching support until Version 3.3.





1.2  CDD Version 3.2 and VAX/VMS Version 4.0

1.2  CDD Version 3.2 and VAX/VMS Version 4.0

You can install CDD Version 3.2 only on a VAX/VMS
Version 4.0 or higher system.



1.3  Installing CDD on a Cluster

1.3  Installing CDD on a Cluster

If you are using CDD Version 3.2 on a VAX/VMS
Version 4.x cluster, you should install the main
dictionary file (CDD.DIC) on a device that is
accessible to the entire cluster.  Otherwise, you
may get some unnecessary lock conflicts between
systems.

You should also make sure that all system logical
names (including CDD$DICTIONARY, which is used to
identify dictionary files) translate in the same way
on each system in the cluster.  Otherwise, the same
subdictionary directory may point to several
different dictionary files, or you may receive a CDD
error that several subdictionary directories point
to the same subdictionary file.



                        1-3



Release Notes

Release Notes


1.4  Underscore Preceding CDD_$TOP

1.4  Underscore Preceding CDD_$TOP

With Version 3.1 and later, you may temporarily
define a logical name for CDD_$TOP.  (See Section
             ___ ______ ____ __________ ______ _____

8.3.1 of the VAX Common Data Dictionary User's Guide
for a description of the circumstances under which
you might define a logical name for CDD_$TOP.)

In path names displayed on the terminal, CDD places
an underscore before CDD_$TOP.  The name CDD_$TOP is
always translated at least once.  After the final
translation, CDD_$TOP will automatically be preceded
by an underscore (__CDD_$TOP).

If a logical name translates to an absolute path
name, then CDD_$TOP will be translated again.  For
example, CDD_$DEFAULT might translate to
CDD_$TOP.JONES.  Then CDD_$TOP is translated a final
time to __CDD_$TOP.



1.5  Using Multiple Versions of CDD Objects with VAX

1.5  Using Multiple Versions of CDD Objects with VAX
     DATATRIEVE

     DATATRIEVE

With CDD Versions 3.0 and later, you can create
multiple versions of dictionary objects.  If you are
using VAX DATATRIEVE, however, you need VAX
DATATRIEVE Version 3.x to access multiple versions
of CDD objects.  Earlier versions of VAX DATATRIEVE
do not support multiple versions.



1.6  The VAX Data Base Management System and

1.6  The VAX Data Base Management System and
     CDDEXC.EXE

     CDDEXC.EXE

The VAX Data Base Management System, also referred
to as DBMS, keeps the CDD message file (CDDEXC.EXE)
open while VAX DBMS is running.  Therefore, even


                        1-4



                                       Release Notes

                                       Release Notes


though a new file is installed as part of the CDD
installation procedure, the old file remains in
place until you shut down VAX DBMS.  You should shut
down VAX DBMS before installing the CDD and start
VAX DBMS again after the CDD has been installed.
                       ___ ______ ____ __________

See Section 1.4 of the VAX Common Data Dictionary
____________ _____

Installation Guide for more information.



1.7  Installing CDD with SYSPRV

1.7  Installing CDD with SYSPRV

If you use the INSTALL utility to install a known
image with the qualifier _/PRIVILEGED=(SYSPRV), you
must install the associated message file with the
qualifier _/SHARED.  Otherwise, the image cannot
access its own message file.  For example, if you
install DMU with SYSPRV, install DMUEXC.EXE, DMU's
message file, with the qualifier /SHARED.



1.8  Path Names Pointing to Subdictionary Files

1.8  Path Names Pointing to Subdictionary Files

When you move a subdictionary file from one system
to another, make sure that the subdictionary's path
name on the new system is the same as it was on the
old system.  Because both VAX DATATRIEVE and VAX
DBMS use full path names by default to locate data
definitions, changing the path name of a
subdictionary will produce errors when DATATRIEVE or
DBMS tries to access definitions in that
subdictionary.

Currently, CDD does not check to ensure that
subdictionary path names remain unchanged.






                        1-5



Release Notes

Release Notes


1.9  The CDDL ALIGNED Clause

1.9  The CDDL ALIGNED Clause

Be careful when you use the CDDL ALIGNED Clause.

o  You should not use the ALIGNED clause in template
   records.  When CDDL stores the template record,
   the position of an aligned field is fixed within
   the record and is not changed when the record is
   copied into another record definition.
   Therefore, the newly created field may not align
   properly in the new record definition.

o  Records created with the ALIGNED clause using
   previous versions of CDDL may not have aligned
   fields properly.  Version 3.1 corrected this
   alignment problem.  However, if you recompile the
   records using the ALIGNED clause, data already
   stored will no longer match the recompiled data
   definition.




1.10  Copying and Renaming a Dictionary Object

1.10  Copying and Renaming a Dictionary Object
      Protected by a Password

      Protected by a Password

Cases may occur where you are granted UPDATE and
CONTROL privileges for an object only through a
password.  If this is true, you cannot copy any
version of another object with the same name as the
protected object to the directory of the protected
object, because DMU COPY provides no way to specify
the protected object's password.

In a case where you are granted the UPDATE privilege
for an object only through a password, you cannot
rename another object as a new version of the
protected object, because DMU RENAME provides no way
to specify the protected object's password.



                        1-6

